Skip to content

Use conda 25.3.0 instead of 24.7.1 in setup-binary-builds - #7753

Merged
atalman merged 1 commit into
mainfrom
atalman-patch-27
Feb 10, 2026
Merged

Use conda 25.3.0 instead of 24.7.1 in setup-binary-builds#7753
atalman merged 1 commit into
mainfrom
atalman-patch-27

Conversation

@atalman

@atalman atalman commented Feb 10, 2026

Copy link
Copy Markdown
Contributor

@vercel

vercel Bot commented Feb 10, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
torchci Ignored Ignored Feb 10, 2026 10:26pm

Request Review

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Feb 10, 2026
@atalman
atalman merged commit bc89543 into main Feb 10, 2026
87 checks passed
@atalman
atalman deleted the atalman-patch-27 branch February 10, 2026 23:04
malfet added a commit that referenced this pull request May 4, 2026
Conda 25.x (now resolved as miniconda `latest`, after #7753 upgraded
conda to 25.3.0) no longer installs `pip` by default when only
`python=X.Y` is requested in `conda create`, which breaks the
`pytorch_pkg_helpers` step in `setup-binary-builds/action.yml`, which
immediately calls `python -m pip install ...` against the new env and
fails with `No module named pip` (e.g. observed in torchcomms wheel
builds).
Fix: add `pip` explicitly to the `conda create` invocation so the env is
usable regardless of conda's default-package behavior.
atalman added a commit that referenced this pull request May 5, 2026
Conda 25.x (now resolved as miniconda `latest`, after #7753 upgraded
conda to 25.3.0) no longer installs `pip` by default when only
`python=X.Y` is requested in `conda create`, which breaks the
`pytorch_pkg_helpers` step in `setup-binary-builds/action.yml`, which
immediately calls `python -m pip install ...` against the new env and
fails with `No module named pip` (e.g. observed in torchcomms wheel
builds).
Fix: add `pip` explicitly to the `conda create` invocation so the env is
usable regardless of conda's default-package behavior.

Co-authored-by: Nikita Shulga <2453524+malfet@users.noreply.github.com>
vmoens pushed a commit to vmoens/test-infra that referenced this pull request May 12, 2026
Conda 25.x (now resolved as miniconda `latest`, after pytorch#7753 upgraded
conda to 25.3.0) no longer installs `pip` by default when only
`python=X.Y` is requested in `conda create`, which breaks the
`pytorch_pkg_helpers` step in `setup-binary-builds/action.yml`, which
immediately calls `python -m pip install ...` against the new env and
fails with `No module named pip` (e.g. observed in torchcomms wheel
builds).
Fix: add `pip` explicitly to the `conda create` invocation so the env is
usable regardless of conda's default-package behavior.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants